You M-U-S-T > > > c-o-n-c-e-t-r-a-t-e as things get more diffi-
cult and complex. Don't be afraid to re-read something!  If you
are making up a batch file  and it doesn't work (they sometimes
DON'T) STOP the file and analyze it. You stop a batch file with
a Control C (for some users that's a control-break). When using
this method to abort a batch processing file, DOS will give you
a message.  Answer Y for yes and you will abort the batch file,
returning to your prompt.  If you answer N for no the file will
continue processing until it finishes or you abort again.
       
To display a batch file use the TYPE command.If you want to re-
vise a file, use EDLIN.  You can use PrtSc with the right shift
key to print what is on the screen(push shift, hold it and then
ALSO press PrtSc. Using EDLIN displays the entire file with all
its line numbers.Look the file over,then print from the screen.
This will save you a lot of time in the long run! Being able to
examine a hard copy of your work product should be very helpful
in finding ERRORS.  FIRST look for DOS commands that are "myss-
spylldedd" (believe it or not)! NEXT look for any other program
commands that are not correctly spelled. LASTLY, check EACH and
EVERY step (line) of the batch file to make sure it >>F-L-O-W-S
EXACTLY the way you wanted it to!  As we move you into the more
complex  batch sub-commands finding errors will become crucial!
